✅ Deploy Preview for gateway-api-inference-extension ready!

Name	Link
🔨 Latest commit	af9a1d5
🔍 Latest deploy log	https://app.netlify.com/projects/gateway-api-inference-extension/deploys/68de9a39b4e99e0008b40b43
😎 Deploy Preview	https://deploy-preview-1673--gateway-api-inference-extension.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dharaneeshvrd
Once this PR has been reviewed and has the lgtm label, please assign danehans for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

/cc @nirrozenbaum
could you please review this fix?

Hi @dharaneeshvrd thanks for the PR. Are we certain this is broken? Looking at the docs it seems like everything is WAI and all other GW implementations have the install step lower down in the guide.

@kfswain Yes currently all GW implementations are having the install step lower down the guide but it seems due to #1381 this recent change, inferencepool helm chart for istio provider requires istio's DestinationRule CRD to be present first. Hence for istio alone moved the installation step before installing the inferencepool helm chart like its being requested in the issue #1649.

@kfswain yup, this is certain. see issue #1649 which I opened after following the quickstart guide and hit that issue.

@dharaneeshvrd I think the current change is not the ideal one.
after this change - the section that is called Deploy the InferencePool and Endpoint Picker Extension is now describing how to install Istio using istioctl.

I was thinking about adding a new Sub-Section like Install Gateway which should include the installation of the specific gateway CRDs (and most Gateways also describe requirement for installing Gateway API CRDs).
so the idea is to make a separation between CRDs installation and actual deployment.
(it's kinda the same idea that we install Inference Extension CRDs in one sub-section, and deploy it in the next sub section).

additionally, when doing this change please pay attention to numbering, cause in current change that was missing (see screenshot below):

Ok If I understood correctly, the guide would have following sections.
Deploy Sample Model Server
Install the Inference Extension CRDs
Install Gateway - New section to add instruction to install Gateway API CRDs and provider specific gateway(CRD & GW itself)
Deploy the InferencePool and Endpoint Picker Extension
Deploy an Inference Gateway - Instruction to deploy Inference Gateway & HttpRoute ...
Remainig section continues as is ...

Hope I can continue with the changes described above.

Ok If I understood correctly, the guide would have following sections. Deploy Sample Model Server Install the Inference Extension CRDs Install Gateway - New section to add instruction to install Gateway API CRDs and provider specific gateway(CRD & GW itself) Deploy the InferencePool and Endpoint Picker Extension Deploy an Inference Gateway - Instruction to deploy Inference Gateway & HttpRoute ... Remainig section continues as is ...

Hope I can continue with the changes described above.

yeah, that sounds good 👍🏻